Throttling access points

ABSTRACT

A technique for controlling the amount of power consumed by access points (APs) of a wireless network involves implementing throttleable APs (TAPs). It would be desirable for the TAPs to be in a relatively low power mode during periods of low activity, and switch to a high power mode in response to increased wireless activity. To that end, a throttling engine can be implemented to throttle TAPs up in power in response to increases in wireless activity, and throttle TAPs down in power in response to decreases in wireless activity.

BACKGROUND

Wireless access points (APs) consume power. Typically a wireless networkincludes many APs that are regularly on to ensure wireless service isavailable to stations accessing the wireless network.

An individual AP draws a moderate amount of power by itself, and manyAPs across a wireless network can collectively draw a large amount ofpower. Such APs may not be servicing clients and may be wasting power.In a business environment or on educational campus, hundreds or eventhousands of APs can be used to provide wireless connectivity throughoutthe network. In similar environments significant amounts of power can beconsumed.

The foregoing examples of the related art and limitations relatedtherewith are intended to be illustrative and not exclusive. Otherlimitations of the related art will become apparent upon a reading ofthe specification and a study of the drawings.

SUMMARY

The following examples and aspects thereof are described and illustratedin conjunction with systems, tools, and methods that are meant to beexemplary and illustrative, not limiting in scope. In various examples,one or more of the above-described problems have been reduced oreliminated, while other examples are directed to other improvements.

A technique for controlling power consumed by access points (APs) of awireless domain involves implementing throttleable APs (TAPs). It wouldbe desirable for the TAPs to be in a low power mode during periods oflow activity, and high power mode during periods of high activity. Tothat end, a throttling engine or wireless domain power saving engine canthrottle TAPs up in power in response to increases in wireless activity,and throttle TAPs down in power, or not throttle the TAPs up in power,in response to decreases in activity.

When there is no wireless activity, the TAPs can be in a sentry mode.However, it may be desirable to keep at least some of the TAPs' radioswith fully enabled functionality. TAPs can be placed in such a way thatthey cover a designated hot spot. At some point, wireless activity mayreach a wireless activity threshold level, and the throttling engine canthrottle one or more of the TAPs up in power to help manage the wirelesstraffic.

A systems administrator can establish a wireless activity thresholdbased upon a wireless activity parameter. The wireless activityparameters can include radio frequency (RF) energy detected, duration ofwireless activity, quality of service (QoS), or other values. Forexample, if client activity is largely voice, it may be desirable tohave higher power APs to ensure that the voice quality is good, whereasit is not as critical if the client activity is largely data. Thethrottling engine can use the threshold to determine when to throttleTAPs up in power.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 depicts an example of a system for controlling power consumptionof a wireless domain based on fluctuations in wireless station activity.

FIG. 2 depicts a flowchart of an example of a method for throttling athrottleable access point (TAP).

FIG. 3 depicts an example of a throttling engine.

FIG. 4 depicts a system for providing power to APs in a power-savingwireless domain.

FIG. 5 depicts an example of a TAP.

FIG. 6 depicts an example of a TAP.

FIG. 7 depicts flowchart of an example of a method for throttling a TAP.

FIG. 8 depicts an example of a computing system that is representativeof the computing systems discussed herein.

DETAILED DESCRIPTION

In the following description, several specific details are presented toprovide a thorough understanding. One skilled in the relevant art willrecognize, however, that the concepts and techniques disclosed hereincan be practiced without one or more of the specific details, or incombination with other components, etc. In other instances, well-knownimplementations or operations are not shown or described in detail toavoid obscuring aspects of various examples disclosed herein.

FIG. 1 depicts an example of a system 100 for controlling powerconsumption of a wireless domain based on fluctuations in wirelessstation activity. The system 100 includes a throttleable access point(TAP) 102-1 and TAPs 102-2 to 102-n (collectively, TAPs 102), a backbonenetwork 104, a TAP controller 106, and a throttling engine 108. Thesystem 100 consumes less power in a relatively low-power state and morepower in a relatively high power state. For illustrative purposes, “lowpower” and “high power” refers to the amount of power consumed by theTAPs 102. It should be noted that the system 100 may or may not alsoinclude non-TAP APs (not shown).

In the example of FIG. 1, the TAPs 102 are access points (APs) that are,in normal operation, continuously on. This enables the TAPs 102 tocommunicate rapidly with wireless stations even when an AP with which awireless station communicates is in a low-power state. A station, asused herein, may be referred to as a device with a media access control(MAC) address and a physical layer (PHY) interface to the wirelessmedium that comply with the IEEE 802.11 standard. As such, in anon-limiting embodiment, the TAPs 102, and APs in general, are stations.In alternative embodiments, a station may comply with a differentstandard than IEEE 802.11, may be referred to as something other than a“station,” and may have different interfaces to a wireless or othermedium. IEEE 802.11a-1999, IEEE 802.11b-1999, IEEE 802.11g-2003, IEEE802.11-2007, and IEEE 802.11n TGn Draft 7.0 (2008) are incorporated byreference. As used in this paper, a system that is 802.11standards-compatible or 802.11 standards-compliant complies with atleast some of one or more of the incorporated documents' requirementsand/or recommendations.

The number of TAPs 102 desirable for a given implementation can dependupon the desired size of a wireless domain. For example, it may bedesirable to locate the TAPs 102 such that they cover the entirearea/space of the wireless domain. The number of TAPs 102 desirable fora given implementation can also depend upon the desired capacity of awireless domain. For example, it may be desirable to locate the TAPs 102such that they can handle the amount of traffic that is expected in aparticular area of the wireless domain. Thus, in one possibleimplementation, the TAPs 102 provide wireless coverage that isoverlapping, perhaps with greater redundancy in areas where a certainamount of wireless traffic is anticipated. In areas where a TAP can bethrottled up in power to meet expected demand, it may be deemedunnecessary to provide a redundant, overlapping TAP. In areas wherethere are redundant, overlapping TAPs, it may be desirable to turn offsome of the TAPs, and only wake them up when active TAPs are unable tomeet traffic demands or quality of service (QoS) requirements, which mayor may not be configurable depending upon the implementation. Animplementation of an AP, provided by way of example but not limitation,includes a TRAPEZE NETWORKS® MOBILITY POINT® (MP®) AP. An implementationof a wireless domain, provided by way of example but not limitation,includes a TRAPEZE NETWORKS® SMART MOBILE® (TRAPEZE SMART MOBILE®)wireless domain.

In operation, the TAPs 102 transmit and receive data (and may thereforebe referred to as transceivers) using one or more radio transmitters.One or more of the TAPs 102 can have more than one associated radio,such as, by way of example but not limitation, a first radio configuredfor 5 GHz transmissions, and a second radio configured for 2.4 GHztransmissions. (Other bands are acceptable, too.) In a non-limitingembodiment, the TAPs 102 transmit and receive information as radiofrequency (RF) signals to and from a wireless station over an Ethernetconnection. The TAPs 102 can transmit and receive information to andfrom associated wireless exchange switches. Connection to a secondwireless exchange switch provides redundancy. An implementation of awireless exchange switch, provided by way of example but not limitation,includes a TRAPEZE NETWORKS® MOBILITY EXCHANGE® (MX®) switch.

Advantageously, the TAPs 102 are APs capable of being throttled tocontrol power consumed by the TAPs 102. The granularity of the throttleis implementation- and/or configuration-specific, but presumably theamount of power above a minimum useful threshold and a maximum possiblethreshold could be set to practically any level, subject to practicalconsiderations. For example, extraordinarily fine settings may cost moreto implement than would be desirable for a person who only wantsrelatively fine settings.

For illustrative purposes, the following power settings are consideredfor the TAPs 102. 1) If an AP is powered down, it, of course, receivesno power. 2) In a standby mode, a subset of the components of the APreceive power, presumably to enable the AP to power up more rapidly thanfrom a powered-down state, to enable LEDs to indicate status, or forsome other applicable reason. 3) As used in this paper, a minimum radiopower setting for an AP is the lowest power setting at which radiofunctionality is at least partially enabled. For example, a minimumradio power setting can be, by way of example but not limitation, asentry mode in which an AP is able to receive data via radio, but nottransmit via radio. Although perhaps of dubious value in someimplementations, a minimum radio power setting might enable transmissionand not reception. It should be noted that in practice a transmittertypically consumes more power than a receiver of the transmitter, butthat distinction is irrelevant to gaining an understanding of thetechniques described in this paper. 4) As used in this paper, a lowpower setting for an AP is a power setting at which radio functionalityis fully enabled for a single spatial stream. For example, a low powersetting can be the lowest power setting at which an AP can both receiveand transmit RF signals in accordance with an implemented standard. 5)As used in this paper, a high power setting for an AP is intended tomean a radio that is receiving sufficient power to support multiplespatial streams. The radio can be implemented as a multiple-inputmultiple-output (MIMO) device with multiple transmitter and receiverantennas. MIMO technology can enable spatial division multiplexing(SDM). SDM spatially multiplexes multiple independent data streams,transferred simultaneously within one spectral channel of bandwidth.Currently, each spatial stream requires an antenna at both thetransmitter and the receiver. So, where SDM is used, a high powersetting for an AP can mean that at least two antenna are enabled, andperhaps an RF chain and analog-to-digital converter for each antenna. Ahigh power setting for an AP can also mean channel bonding isimplemented, which can mean simultaneous transmission over multiplenon-overlapping channels. For example, a 40 MHz mode of operation canuse two adjacent 20 MHz bands. (While this doubles the throughput on thephysical layer, MAC and user level throughput will not double.) A highpower setting for an AP can mean both MIMO and channel bonding, which issupported by the IEEE 802.11n (draft) standard, for example. 6) As usedin this paper, a maximum radio power setting for an AP is intended tomean a radio that is using multiple spatial streams at maximum power. 7)As used in this paper, a relatively low power setting can have avariable associated power, but will typically be referred to in contrastto a relatively high power setting. As such, a relatively low powersetting is between a minimum radio power setting (inclusive) and arelatively high power setting (exclusive); and the relatively high powersetting is between the relatively low power setting (exclusive) and themaximum radio power setting (inclusive). On the other hand, when makingreference to a wireless domain, relatively low power can mean theaggregated power consumption of TAPs 102 is lower than at a relativelyhigh power. Examples of TAPs are discussed in further detail later.

In a non-limiting embodiment, the TAPs 102 are hardware units that actas a communication hub by linking wireless stations to the backbonenetwork 104. This can enable, the TAPs 102 to connect users to otherusers within the network and/or to serve as the point of interconnectionbetween a WLAN and a wired network. The connection to the backbonenetwork 104 is sometimes referred to as a “link.” The APs act asgenerally transparent bridges connecting wireless stations to thebackbone network 104. In 802.11 standards-compliant and some otherimplementations, the backbone network 104 is an Ethernet network, butthis is not mandatory for all implementations. In some implementations,the backbone network 104 is a wired backbone network, though thebackbone network 104 could conceivably be implemented as a wirelessbackbone (presumably coupled to a wired network at some point). In atypical implementation, the backbone network 104 couples the TAPs 102 tonetwork resources (not shown). Where the backbone network 104 isimplemented as an 802.11-compatible system, the backbone network 104 istypically connected to the outside world through what is typicallyreferred to as a portal (not shown).

In the example of FIG. 1, the TAP controller 106 is coupled to thebackbone network 104. The TAP controller 106 can include practically anytype of device that is capable of communicating with a communicationsnetwork, such as, by way of example but not limitation, a server classcomputing system or a workstation. The TAP controller 106 can bedistributed or centrally located. The TAP controller 106 can include asingle controller for all of the TAPs 102; multiple controllers, one foreach of the TAPs 102; or some arbitrary or convenient number ofcontrollers, each for controlling a subset of the TAPs 102. In someimplementations, the TAP controller 106 controls a “dumb” AP, while inother implementations, functionality of the TAP controller 106 can beimplemented in whole or in part in a “smart” AP. The TAP controller 106may or may not include a wireless switch. In some implementations, theTAP controller 106 is aware of associations of stations to APs of thesystem 100. In operation, controllers are engines implemented in specialpurpose hardware, firmware, or software embodied in a computer readablemedium for execution by a processor.

In the example of FIG. 1, the TAP controller 106 is coupled to thethrottling engine 108. As used in this paper, an engine includes aprocessor and, typically, firmware or software modules that are executedby the processor. Depending upon implementation-specific or otherconsiderations, an engine can be centralized or its functionalitydistributed. An engine can include special purpose hardware, firmware,or software embodied in a computer-readable medium for execution by theprocessor. As used in this paper, a computer-readable medium is intendedto include all mediums that are statutory (e.g., in the United States,under 35 U.S.C. 101), and to specifically exclude all mediums that arenon-statutory in nature to the extent that the exclusion is necessaryfor a claim that includes the computer-readable medium to be valid.Known statutory computer-readable mediums include hardware (e.g.,registers, random access memory (RAM), non-volatile (NV) storage, toname a few), but may or may not be limited to hardware.

The throttling engine 108 is capable of determining when wirelessactivity is above a threshold, using wireless activity data typicallyprovided at least in part by the TAPs 102 that are at least in sentrymode. When the throttling engine 108 determines that wireless activityis above a threshold, the throttling engine 108 informs the TAPcontroller 106 that one or more of the TAPs 102 should be throttled upin power. Depending upon the implementation and/or embodiment, the TAPsengine 108 may or may not inform the TAP controller 106 when wirelessactivity is below a threshold. For example, the TAPs engine 108 mayinform the TAP controller 106 that one of the TAPs 102 should bethrottled up in power when a threshold is exceeded, and fail to informthe TAP controller 106 when the threshold is not exceeded. When the TAPcontroller 106 receives the throttle request from the throttling engine108, the TAP controller 106 can throttle the relevant TAP up in power,which then stays at that power level for a predetermined period of time.If the TAP is not throttled again, then it can power down, enter sentrymode, drop to a low power mode, or step down gradually from a currentpower level after the predetermined period of time. Thus, there is noneed for a throttle down in power command. In another embodiment, one ormore of the TAPs 102 could be at a maximum radio power setting as adefault, and receive throttle commands to throttle power down. Inanother embodiment, one or more of the TAPs 102 could remain in a givenstate until an throttle up or throttle down command causes the TAP tochange, respectively, to a higher or lower state.

In the example of FIG. 1, stations 112, 114 can include a laptop,desktop computing device, portable digital assistant (PDA), wirelesstelephone, or any other applicable computing device capable ofcommunications on a wireless network. The stations 112, 114 can complywith any wireless standard for the transmission of data, or may complywith none at all. The stations 112, 114 include a radio for transmissionof data and may have any other known or convenient interface to awireless network or other medium. Typically, the stations 112, 114 cantransmit and receive data as RF signals using the radio or otherinterface.

In the example of FIG. 1, in operation, the TAPs 102 are assumed toinitially be in a low power state. Since the TAPs 102 are at least insentry mode, the TAP controller 106 can monitor the wireless domainthrough the TAPs 102, which provide wireless activity data to the TAPcontroller 106 and/or the throttling engine 108. For illustrativepurposes, the station 112 is turned on or comes within range of thewireless domain, and is wirelessly coupled to the TAP 102-1. Forillustrative purposes, it is assumed that the station 112 does notprovide sufficient wireless activity to pass a wireless activitythreshold. Therefore, the TAP 102-1 remains in a low power mode.

Later, additional stations (not shown) may be turned on or come withinrange of the wireless domain, but still not provide sufficient wirelessactivity to pass the wireless activity threshold. At some point, thestation 114 is turned on or comes within range of the wireless domain,and the wireless activity at the TAP 102-1 passes the wireless activitythreshold. The throttling engine 108 receives the wireless activitydata, determines that the wireless activity threshold is exceeded(perhaps for a certain duration, depending upon the implementationand/or embodiment), and informs the TAP controller 106 that the TAP102-1 is to be throttled up in power. The TAP controller 106 throttlesup the TAP 102-1, the TAP 102-1 throttles up to a higher power state andremains at the higher power state for a period of time. At some pointbefore or after the TAP 102-1 is throttled up, the station 114 iscoupled to the TAP 102-1.

While the wireless activity exceeds the wireless activity threshold, thethrottling engine 108 will continue to inform the TAP controller 106that the TAP 102-1 is to be throttled up to the higher power state, theTAP controller 106 keeps the TAP 102-1 throttled up to the higher powerstate with a throttle command, and the TAP 102-1 remains at the higherpower state for a period of time.

Later, additional stations (not shown) may be turned on or come withinrange of the wireless domain, and the throttling engine 108 causes theTAP 102-1 to eventually throttle up to a maximum radio power. The TAP102-1 can perhaps continue to handle traffic as even more stations (notshown) are turned on or come within range. At some point, the throttlingengine 108 determines, with the addition of the wireless station 116,that the TAP 102-1 cannot handle all of the wireless traffic near it,and sends a throttle command to the TAP 102-2, which, for illustrativepurposes, is assumed to overlap with the TAP 102-1 over at least aportion of the wireless domain. The station 116 (or perhaps some otherstation) may or may not be handed off by the TAP 102-1 to the TAP 102-2.

When the wireless activity drops below the wireless activity threshold,the throttling engine 108 stops informing the TAP controller 106 of theneed for throttling up, and after a period of time is up the TAP 102-1throttles down. At some point, when wireless traffic reaches a low pointor stops entirely, the TAP 102-1 drops to the low power state once more.

FIG. 2 depicts a flowchart 200 of an example of a method for throttlinga TAP. The method is organized as a sequence of modules in the flowchart200. However, it should be understood that these and other modulesassociated with other methods described herein may be reordered forparallel execution or into different sequences of modules.

In the example of FIG. 2, the flowchart 200 starts at module 202 wherewireless activity in a wireless domain is monitored. Wireless activityis typically, though not necessarily or only, detected when RFtransmissions from one or more stations are received at an AP, such as aTAP that is at least in sentry mode, of the wireless domain. The APssend wireless activity data to a controller and/or throttling engine foranalysis. The wireless activity data may or may not be pre-processed atthe AP, depending upon the implementation and/or embodiment. Thewireless activity data at least can provide information about the amountof wireless activity in the wireless domain, and the controller or someother engine knows about the capabilities of the APs of the wirelessdomain in handling the load. So a comparison of the capabilities of theAPs and the wireless activity can indicate whether the capabilities ofthe APs are being pushed beyond an acceptable threshold.

In the example of FIG. 2, the flowchart 200 continues to module 204where a wireless activity threshold is determined. The wireless activitythreshold can be set by a human (e.g., systems administrator) orsoftware agent. The threshold can be based upon an estimated amount ofwireless activity, the ratio of non-AP stations to APs, or otherparameters. The key with respect to setting the wireless activitythreshold is to ensure, as much as is possible, that APs can bethrottled up in power when the wireless traffic reaches a point (andperhaps remains at or above that point for a period of time) where adecision-maker has determined that the APs cannot handle the wirelesstraffic adequately. Whether the APs can handle the wireless trafficadequately may be based on measurements, empirical or historical data,QoS considerations, or even opinion.

In a static threshold implementation, the wireless activity threshold isstatic in that it does not vary in response to the wireless activitydata obtained through the APs of the wireless domain. In this simpleimplementation, determining the wireless activity threshold involvesreading a threshold value from memory for comparison with currentestimated wireless activity. If there are multiple power levels for aTAP, then the TAP can be associated with a respective multiple staticwireless activity thresholds. (It may be noted that the number ofwireless activity thresholds can equal the number of power levels plusone if the lowest power level does not have an associated wirelessactivity threshold.) If there are multiple TAPs, then each of the TAPscan be throttled at the same or different static wireless activitythresholds.

In a dynamic threshold implementation, the wireless activity thresholdis dynamic in that it varies in response to the wireless activity dataobtained through the APs of the wireless domain. For example, ifwireless activity is fluctuating rapidly over time, it may be desirableto change the threshold. This may cause a TAP to be less susceptible tothrottling down when wireless activity dips, which might be considereddesirable because of anticipated increases in wireless activity in theshort term; or may cause the TAP to be less susceptible to throttling upwhen wireless activity increases, which might be considered desirable ifit is predicted that the wireless domain can handle a momentary increasein activity. Dynamic thresholds can be set using historical wirelessactivity data, including both recent history, and long-term history. Anexample of long-term history might include increases in wirelessactivity at certain days during the week (e.g., Monday to Friday) atcertain times (e.g., 8 A.M., perhaps when many people enter the wirelessdomain at the start of work). Dynamic thresholds can also be implicitlyset in some cases. For example, if a station informs, either implicitlyor explicitly, of a need to use relatively high amounts of bandwidth(e.g., for a large file download), dynamic thresholds could bedynamically dropped near the station in anticipation of the increasedactivity. In some implementations, TAP throttling can be accomplishedrelatively rapidly, which reduces the need for dynamic thresholds. Inother cases, TAPs might be relatively slow in throttling up, makingdynamic thresholds more valuable to enable anticipation of wirelessresource needs.

In a first threshold example, each TAP has its own one or more wirelessactivity thresholds. When an individual TAP reaches one of itsthresholds, it is throttled up in power. TAPs throughout the wirelessdomain may have the same values for each of their one or morethresholds, or different TAPs could have different thresholds. The TAPsin this first threshold example are greedy in the sense that theythrottle up in response to activity around themselves, withoutconsideration of the needs of the wireless domain. This can beadvantageous because it is simple, and greedy throttling of power atleast addresses the issue of a TAP-local need for increased power.

In a second threshold example, a first TAP can influence the throttlingof a second TAP. For example, reaching a wireless activity threshold ata first TAP causes the first TAP and a second TAP to throttle up inpower. Alternatively, reaching a first wireless activity threshold for afirst TAP causes the first TAP to be throttled up in power and reachinga second wireless activity threshold for the first TAP causes both thefirst TAP and a second TAP (or perhaps only the second TAP) to bethrottled up in power. At least the first TAP in this second thresholdexample is collaborative in the sense that it (or a controller higher upthe chain) tells a second TAP to throttle up in response to wirelessactivity near the first TAP.

As a variation on the second threshold example, say a first TAP and asecond TAP have overlapping coverage of at least a portion of a wirelessdomain. When the first TAP reaches one of its thresholds, both the firstTAP and the second TAP (and perhaps all other TAPs that have overlappingcoverage with respect to the first TAP) are throttled up in power. Thiscould also be accomplished for “greedy” TAPs where the first TAP and thesecond TAP reach their respective thresholds and throttle up in responseto increased wireless activity, without any collaboration between thefirst TAP and the second TAP.

As a third threshold example, a first TAP and a second TAP may haveoverlapping coverage. If wireless activity at both the first TAP and thesecond TAP increases sufficiently to make throttling up desirable, thefirst TAP may throttle up and inform the second TAP that throttling upis not necessary. In this way, in response to increased wirelessactivity, only one of the TAPs throttles up in power to see if it canhandle the increased wireless load. It may be considered desirable tothrottle the first TAP up to maximum before throttling up any redundantTAPs. Or it may be considered desirable to gradually throttle upoverlapping TAPs, rather than to favor running particular ones of theTAPs at higher power.

In a fourth threshold example, each TAP in the wireless domain could bethrottled up in power when wireless activity in a wireless domainreaches one or more global wireless activity threshold. The one or moreglobal wireless activity thresholds can be considered global withrespect to the wireless domain because it does not take into accountwireless activity in different areas of the wireless domain. As the sizeof the wireless domain increases, the desirability of more localwireless activity thresholds increases because wireless activity may behigh in one corner of the wireless domain, but low in another corner ofthe wireless domain; so throttling up power when wireless activityexceeds a global wireless activity threshold will not help if a TAP isthrottled up in power in a low activity corner of the wireless domain. Amore local solution may be to have wireless activity thresholds for“bunches” of TAPs, presumably located relatively near one another.

In a first local wireless activity threshold example, a plurality of APshave wireless activity thresholds associated with them, and when awireless activity threshold is exceeded within range of an AP, TAPs nearthe AP (and the AP, if it is a TAP) are throttled up in power. Each APcan have multiple wireless activity thresholds, and as each wirelessactivity threshold is exceeded, the TAPs are throttled up in power a bitmore.

In a second local wireless activity threshold example, a plurality ofAPs have wireless activity thresholds associated with them, and when awireless activity threshold is exceeded within range of an AP, a TAPnear the AP (or the AP, if it is a TAP) is throttled up in power. TheTAP can also have a wireless activity threshold associated with it, andwhen the wireless activity threshold is exceeded, another TAP isthrottled up in power, which may or may not also have a wirelessactivity threshold associated with it. In these local wireless activitythreshold examples, each wireless activity threshold can be thought ofas local with respect to an AP because the wireless activity near the APis taken into consideration when determining whether the wirelessactivity threshold is exceeded.

More sophisticated implementations may include setting “floating”thresholds that vary depending upon the quantity, nature, and/orlocation of wireless activity within the wireless domain. As usedherein, a wireless activity threshold that depends upon local wirelessactivity, but is not statically associated with a particular AP, isreferred to as a “floating” wireless activity threshold, as opposed toan AP-specific wireless activity threshold, where it is desirable todraw a distinction between the two. A floating wireless activitythreshold may be adjusted dynamically in response to the wirelessactivity data received while monitoring wireless activity. Dependingupon the implementation, embodiment, configuration, and/or wirelessactivity data, determining a wireless activity threshold can dynamicallyincrease or decrease in complexity depending upon conditions within thewireless domain. As used here, “dynamically” means “in response tochanging conditions within the wireless domain.” In these moresophisticated implementations, each wireless activity threshold can bethought of as local with respect to a potentially changing subset of APsin the wireless domain. For example, if wireless activity near a firstsubset of APs causes a first TAP to be throttled up in power, it may bethat a second overlapping subset of APs no longer “needs” a second TAPat its current power; the subset of APs associated with the dynamicwireless activity threshold changes over time. In this example, picturea wave of wireless activity that sweeps through a wireless domain,throttling TAPs up in power for a subset of APs on the crest of thewave, and throttling TAPs down in power (or not throttling up) TAPs asthe wave passes.

In the example of FIG. 2, the flowchart 200 continues to decision point206 where it is determined whether wireless activity exceeds a wirelessactivity threshold. The wireless activity threshold can be global,relatively local, local, AP-specific, or floating, depending upon theimplementation and/or embodiment. Depending upon the implementationand/or embodiment, the wireless activity threshold can be exceeded if RFenergy exceeds a certain amount, the number of non-AP stations to APsexceeds a certain ratio, traffic-specific (e.g., QoS) conditions aredesired, and/or some other condition is desired.

If it is determined that the wireless activity threshold is not exceeded(206-N), then the flowchart 200 continues to module 208 where a TAP isnot throttled up in power. In a first implementation, “not throttlingthe TAP up in power” requires no action, and the TAP will presumablythrottle down over time without instructions. In a secondimplementation, each TAP has a setting, and “not throttling the TAP upin power” may also include lowering the setting so as to throttle theTAP down in power, if the wireless activity drops below a secondwireless activity threshold (where the wireless activity threshold ofdecision point 206 is a first wireless activity threshold). In eithercase, the flowchart 200 returns to module 202 and continues as describedpreviously.

If, on the other hand, it is determined that the wireless activitythreshold is exceeded (206-Y), then the flowchart 200 continues tooptional decision point 210 where it is determined whether a duration ofwireless activity exceeds a timer threshold. The timer threshold can beinherently or explicitly set to zero, which means that the determinationis always “yes.” However, since TAPs can take time to throttle up inpower, brief spikes in wireless activity might cause a TAP to throttlepower up and down more frequently than is desirable. To prevent TAPsfrom powering up and down too frequently, a timer can be set. When theduration of wireless activity exceeds the duration of the timer, thetimer threshold is exceeded.

It should be noted that TAPs can be capable of throttling powerrelatively rapidly, which may reduce or eliminate the need for a timer.For at least this reason, the decision point 210 is optional, andwhenever the wireless activity exceeds the threshold, the flowchart 200proceeds directly to module 212 (described below). Whether removing thetimer is desirable can depend upon the capabilities of the TAP, theparticular implementation, the opinions of the humans managing thewireless domain, or other factors.

If it is determined that the duration of wireless activity does notexceed a timer threshold (210-N), then the flowchart 200 returns tomodule 208 and continues as described previously. It may be noted thatif the optional decision point 210 is not used in an implementation,then 210-N will not exist for the implementation.

If, on the other hand, it is determined that the duration of wirelessactivity exceeds a timer threshold (210-Y), then the flowchart 200continues to module 212 where a TAP is throttled up in power. The TAPcan be throttled up in power in many ways. For example, power can beapplied to the TAP, a group of inactive components can be activated,instructions can be transmitted to the TAP to cause the TAP to resumenormal operation, or another known or convenient throttling scheme canbe applied. In a first implementation, the TAP remains throttled up fora period of time that is greater than the time it takes to traverse theflowchart 200 back to decision point 206. This ensures that the TAP willnot power down while wireless activity remains above the wirelessactivity threshold, but before receiving subsequent agitation. This timeperiod can also cause the TAP to remain powered up for some period oftime after wireless activity drops below the wireless activitythreshold, which can ensure that the TAP remains powered up during abrief drop in wireless activity. In a second implementation, the TAPremains powered up until throttled down. In any case, the flowchart 200returns to module 202 and continues as described previously.

FIG. 3 depicts an example of a wireless domain power saving engine 300.The wireless domain power saving engine 300 can include a controller ora portion of a controller, a controller can include the wireless domainpower saving engine 300 or a portion of the wireless domain power savingengine 300, or a controller and the wireless domain power saving engine300 can be distinct with respect to one another. The system 300 includesan AP interface 302, a wireless activity analysis module 304, a wirelessactivity threshold module 306, an optional timer 308, and a processor310. The processor 310 is coupled to the wireless activity analysismodule 304, the wireless activity threshold module 306, and the optionaltimer 308.

In the example of FIG. 3, the AP interface 302, receives wirelessactivity data from controllers, stations, and/or other devices orengines associated with a wireless domain, or, more generally, acommunications network. The AP interface 302 can interpret the wirelessactivity data in terms of a number, ratio, or other known or convenientvalue. For example, the wireless activity data can include a numberassociated with the number of wireless packets received at an AP and/orsent from the AP, the ratio of non-AP stations to APs in a wirelessdomain or a portion of the wireless domain, etc. The wireless activitydata can be in a general format that is similar to that provided fromthe APs of the wireless domain, or data from the APs can be preprocessedor compiled at, by way of example but not limitation, a controller orsome other intermediate device.

In the example of FIG. 3, the wireless activity analysis module 304receives the wireless activity data from the AP interface 302. A module,as used in this paper, can include hardware, firmware, or softwareimplemented in hardware or firmware for execution by a processor. Thewireless activity analysis module 304, together with the processor 310,can be referred to as a wireless activity analysis engine. The wirelessactivity analysis module 304 can receive a wireless activity thresholdvalue from the wireless activity threshold module 306 and a timerthreshold from the optional timer 308. In operation, the wirelessactivity analysis engine compares the wireless activity data to thewireless activity threshold, determines whether the wireless activitythreshold has been exceeded and, if applicable, whether the wirelessactivity threshold has been exceeded for a requisite amount of time(i.e., the timer threshold has been exceeded). If the wireless activitythreshold has been exceeded for the requisite amount of time, thewireless activity analysis engine sends TAP throttling data through theAP interface 302. The TAP throttling data can be sent directly to a TAP,causing the TAP to throttle itself up in power, or the TAP throttlingdata can be sent to an intermediate device, such as a controller, whichcan use the TAP throttling data to determine which TAPs to throttle, ifany. A partially disabled TAP may be able to “self-start” when given athrottling instruction, and a completely powered-down TAP may receivepower instead of or in addition to a throttling instruction. In analternative embodiment, the wireless activity analysis engine sends TAPthrottling data as a report, regardless of whether TAP throttling iscalled for.

In the example of FIG. 3, the wireless activity threshold module 306provides a wireless activity threshold to the wireless activity analysismodule 304. The wireless activity threshold module 306, together withthe processor 310, can be referred to as a wireless activity thresholdengine. An initial wireless activity threshold value can be input by ahuman or software agent. The value represents an amount of wirelessactivity within a wireless domain or a portion of the wireless domain atwhich it is desirable (according to the agent or by default) to throttlea TAP up in power to handle some of the load. Depending upon theimplementation and/or embodiment, the wireless activity threshold module306 may or may not receive feedback from the wireless activity analysismodule 304 that enables the wireless activity threshold module 306 todynamically alter threshold values based upon wireless activity within awireless domain or a portion of the wireless domain.

In the example of FIG. 3, the optional timer 308 provides a timerthreshold to the wireless activity analysis module 304. The timerthreshold may be represented, at least conceptually, as a number value.The optional timer 308 can also provide a first timestamp at a time whenthe wireless activity analysis engine determines that a wirelessactivity threshold has been exceeded, and a second timestamp at a latertime. The timer threshold is exceeded when the difference between afirst timestamp and a second timestamp is greater than the number valueof the timer threshold. As used here, a timestamp is intended to includeany value associated with a timer such that the wireless activityanalysis module 304 can compare a first timestamp to a second timestampto determine, or at least approximate, an amount of time has elapsedbetween receiving the first timestamp and the second timestamp. Theexact nature or implementation of the timer 308 is not critical. Thetimer 308 is optional because, depending upon the implementation,throttling may occur on an as-needed bases rather than on a delayedbasis to reduce the likelihood of wasteful fluctuations in power levelsof TAPs.

In the example of FIG. 3, in operation, wireless activity data isprovided from the AP interface 302, a wireless activity threshold isprovided from the wireless activity threshold module 306, and a timerthreshold and timestamp is provided from the optional timer 308 to thewireless activity analysis module 304. The wireless activity analysismodule 304 determines whether estimated wireless activity (derived atleast in part from the wireless activity data) exceeds the wirelessactivity threshold, and has exceeded the wireless activity threshold fora duration that exceeds the timer threshold. When the wireless activitythreshold and the timer threshold (if applicable) are both exceeded, anddepending upon the implementation even when not exceeded, the wirelessactivity analysis engine sends TAP throttling data through the APinterface 302. As previously indicated, the AP interface 302 can includea direct link to an AP, or an indirect link (e.g., through acontroller).

FIG. 4 depicts a system 400 for providing power to APs in a power-savingwireless domain. The system 400 includes a power supply unit (PSU) 402,an AP 404, a throttling engine 406, a switch 408, and a TAP 410. Forillustrative simplicity, only one each of an AP and TAP are depicted,but, depending upon the implementation, there can be multiple APs orTAPs in a wireless domain. The TAP 410 includes optional low power (LP)components 412 and high power (HP) components 414.

In the example of FIG. 4, the PSU 402 can be any known or convenientpower source. Although in the example of FIG. 4, the PSU 402 appears tobe external with respect to the APs, the PSU 402 can be implemented asbatteries within one or more of the APs, and hence “distributed” withineach of the APs. Also, the PSU 402 could be implemented as multiplepower sources or provide power over Ethernet (PoE).

In the example of FIG. 4, the AP 404 is operationally connected to thePSU 402. This is intended to show that the AP 404 receives constantpower and is, therefore, continuously powered up. Because it always haspower, the AP 404 can be configured for continuous monitoring of thewireless domain, if desired.

In the example of FIG. 4, the throttling engine 406 can be implementedas described with reference to FIG. 3, or using other techniquesdescribed in this paper.

In the example of FIG. 4, the switch 408 is coupled to the throttlingengine 406. In this example, the switch 408 is closed (i.e., on) whenthe throttling engine 406 provides TAP throttling data indicating thatthe TAP 410 is to be throttled up in power. In this example, the switch408 is open (i.e., off) when the throttling engine 406 does not provideTAP throttling data indicating that the TAP 410 is to be throttled up inpower. The switch 408 is intended to be a conceptual representation ofwhen power is provided to the HP components 414 of the TAP 410, not anactual hardware switch or transistor, though it could be implemented assuch; the switch 408 can be a “logical” switch.

In the example of FIG. 4, the TAP 410 includes LP components 412 thatare operationally connected to the PSU 402. Thus, the LP components 412are always on. The LP components 412 might include, by way of examplebut not limitation, components that consume relatively little power, aradio receiver, a single antenna capable of sending and receiving RFsignals, or some other component. In an AP, the radio often consumes themost power; so if the LP components 412 include everything except theradio, the TAP 410 can conserve significant power in sleep mode.Although it consumes power, it might be desirable to make the radioreceiver (but not transmitter) one of the LP components 412 to ensurethat the TAP 410 can listen for wireless activity. If the radio receiveris one of the LP components 412, then the TAP 410 may be able to enter a“sentry mode” and help monitor the wireless domain. Finally, although itconsumes even more power, it might be desirable to make one of the LPcomponents 412 an antenna capable of sending and receiving in a firstspatial stream. In this way, the TAP 410 always has full APfunctionality. For example, an 802.11-n-compliant TAP 410 might includea single antenna in the LP components 412, which would give the TAP 410full AP functionality in a low power mode, but not full 802.11n APfunctionality (with multiple spatial streams).

The HP components 414, on the other hand, receive power from the PSU 402through the switch 408. Thus, the HP components 414 are only on when theswitch 408 is closed. The HP components 414 might include, by way ofexample but not limitation, a radio transmitter, a radio receiver,multiple antennae, or any other component. An 802.11-n-compliant TAP 410might include one or more antennae in the HP components 414, which wouldgive the TAP 410 the ability to use multiple spatial streams in a highpower mode. In a typical implementation, this can also cause a processoron the TAP 410 to consume more power due to an increased computationalload.

The example of FIG. 4 is intended to illustrate a simple, conceptualexample. More complex TAPs may have multiple power levels, such asmaximum power, high power, low power, sentry (e.g., transmitters off),standby (e.g., radios off), and sleep (e.g., powered down). The numberof discrete power levels is implementation-specific, but can easilyrange from a few to tens, hundreds, or even more.

In the example of FIG. 4, in operation, the AP 404 and the LP components412 of the TAP 410 receive power from the PSU 402. The TAP 410 is, forillustrative purposes, assumed to be in a low power mode (with a singleantenna operational for sending and receiving), which for this examplemeans that the switch 408 is open and the HP components 414 aredisabled. The AP 404 monitors nearby stations and provides wirelessactivity data to the throttling engine 406. The throttling engine 406determines that the wireless activity has passed a wireless activitythreshold and, if applicable, a timer threshold. So the throttlingengine 406 sends a command to the switch 408 to close the switch 408,thereby providing power from the PSU 402 to the HP components 414 of theTAP 410. Alternatively, the throttling engine 406 could provide aninstruction to the AP 404, which then instructs the TAP 410 to enter HPmode. When the TAP 410 is powered up, it can perform any of thefunctions that the AP 404 can, assuming it is configured to do so.Later, when wireless activity dips below a wireless activity threshold,the throttling engine 406 may open the switch 408, causing the TAP 410to drop back into LP mode.

It should be noted that the AP 404 and the TAP 410 could be incorporatedas a single device, where the LP components 412 provide the samefunctionality as described above with reference to the AP 404. In suchan implementation, the TAP 410 could be referred to as a self-throttlingTAP.

FIG. 5 depicts an example of a TAP 500. The TAP 500 includes acontroller interface 502, a sleep timer 504, a switch 506, a powerinterface 508, LP components 510, a first antenna 512, a second antenna514, and an optional I/O interface 516.

In the example of FIG. 5, the controller interface 502 can beimplemented, by way of example but not limitation, as an interface to awired backbone to which a controller is coupled. The interface can be,by way of example but not limitation, an Ethernet interface. It wouldtypically be undesirable to disable the controller interface 502 whenthe TAP 500 is asleep because it takes relatively little power to keep,for example, an Ethernet interface, enabled. However, in animplementation, the controller interface 502 could be powered down andthe TAP 500 would presumably first receive power from the powerinterface 508, power up some low power components including thecontroller interface 502, and go from there.

In the example of FIG. 5, the sleep timer 504 can be implemented as atimer having a start time and an end time. The timer can be reset whenthe sleep timer 504 receives a wakeup command, and continues runningfrom the start time to the end time. While the timer is running, thesleep timer 504 outputs a wakeup signal. When the timer reaches the endtime, the sleep timer 504 ceases outputting the wakeup signal. It can beadvantageous to use a pseudo random number generator to set the end timeof the timer to prevent coincidental deactivation of multiple TAPs, eachhaving the same timer duration; simultaneous deactivation of many TAPscould be undesirable. As a general rule, if the end time is set to arelatively high value, the TAP will consume relatively large amounts ofpower. On the other hand, if the end time is set to a relatively lowvalue, the TAP is more likely to need to be throttled up in power priorto providing a desired level of service, which, at least potentially,can result in delay.

In the example of FIG. 5, the switch 506 is coupled to the sleep timer504 and can be implemented as a hardware or logical switch in anyapplicable known or convenient manner. While the switch 506 receives thewakeup signal from the sleep timer 504, the switch 506 is closed (i.e.,on). While the switch 506 is not receiving the wakeup signal from thesleep timer 504, the switch 506 is open (i.e., off).

In the example of FIG. 5, the power interface 508 can be implemented asan interface to a PSU (e.g., an external power source, a battery, orsome other power source) in any applicable known or convenient manner.In certain implementations, the controller interface 502 and the powerinterface 508 can be thought of as a single interface. For example, aPoE system provides both power and data through an Ethernet interface.

In the example of FIG. 5, the power interface 508 couples power from apower source to the LP components 510. The LP components 510, in thisexample, include components of the TAP 500 that draw power, such as aprocessor, memory, etc., but excluding the second antenna 514.

In the example of FIG. 5, the power interface 508 also couples powerfrom a power source to the first antenna 512. The LP components 510 arecoupled to the first antenna 512; the coupling is represented in theexample of FIG. 5 as a dashed line. The LP components 510 provide thefirst antenna 512 with whatever functionality is needed for the firstantenna 512 to send and receive RF data a first spatial stream.

In the example of FIG. 5, the power interface 508 couples power from apower source to the second antenna 514 so long as the switch 506 isclosed. In this way, the second antenna 514 draws power only when thesleep timer 504 is outputting a wakeup signal, and the second antenna514 does not draw power (i.e., it is off) when the sleep timer 504 isnot outputting a wakeup signal.

In the example of FIG. 5, the optional I/O interface 516 can beassociated with a display (e.g., light emitting diodes (LEDs) or aliquid crystal display (LCD)) or input device (e.g., a power button ordial). A display can, for example, enable a user to see whether the TAPis asleep, in sentry mode, operating at low power, or operating at highpower at a glance. An input device can, for example, enable a person toforce the TAP to remain in a full power mode. The I/O interface 516 isoptional because control of the AP could, in at least someimplementations, be handled entirely through the controller interface502 and/or the LP components 510.

Advantageously, a TAP implemented as described with reference to FIG. 5causes the TAP to power up when a throttling engine determines that itshould, and to remain powered up even if there is a brief period of lessactivity. Thus, the TAP will not power up and power down too often. Whatconstitutes “too often” can depend upon the amount wireless activity,the type of wireless activity, and/or the opinion of an agent who canset the duration of the sleep timer.

Even in an implementation where power can be throttled up or down withrelatively immediate results, the data provided about wireless activityis likely to be in discrete units. For example, the wireless activitydata may come as payload in packets or frames. Thus, advantageously, thesleep timer can keep the TAP from dropping in power before an updateregarding the wireless activity data is received.

FIG. 6 depicts an example of a TAP 600. The TAP 600 includes acontroller interface 602, a throttle 604, a power interface 606, LPcomponents 608, and HP components 610. FIG. 6 is intended to illustratean example of a device with no sleep timer.

The controller interface 602 receives wireless activity data or TAPthrottling data from a controller. The throttle 604 throttles (up ordown) the power from the power interface 606 to the HP components 610,while the LP components 608 are not throttled. It may be noted,depending upon which components are characterized as LP, that increasedpower to the HP components 610 may increase power consumption by the LPcomponents 608. For example, if the HP components include an additionalantenna that is activated with increased power from the power interface606 (due to throttling up by the throttle 604), and the LP componentsinclude a processor, the processor may consume more power whenprocessing data associated with multiple spatial streams necessitated bythe activation of the additional antenna than it did for a single (orfewer) spatial streams.

FIG. 7 depicts a flowchart 700 of an example of a method for throttlinga TAP. The method is organized as a sequence of modules in the flowchart700. However, it should be understood that these and other modulesassociated with other methods described herein may be reordered forparallel execution or into different sequences of modules.

In the example of FIG. 7, the flowchart 700 starts at module 702 wherewireless activity in a wireless domain is monitored. Wireless activityis typically, though not necessarily or only, detected when RFtransmissions from one or more stations are received at an AP, such as aTAP that is at least in sentry mode, of the wireless domain. The APssend wireless activity data to a controller and/or throttling engine foranalysis. The wireless activity data may or may not be pre-processed atthe AP, depending upon the implementation and/or embodiment. Thewireless activity data at least can provide information about the amountof wireless activity in the wireless domain, and the controller or someother engine knows about the capabilities of the APs of the wirelessdomain in handling the load. So a comparison of the capabilities of theAPs and the wireless activity can indicate whether the capabilities ofthe APs are being pushed beyond an acceptable threshold.

In the example of FIG. 7, the flowchart 700 continues to module 704where a power level appropriate for the wireless activity is determined.The determination can be by a human for static determinations, or by asoftware agent for static or dynamic determinations. The “appropriatepower level” can be referred to as a desired throttle setting, since anyparticular throttle setting can be at least roughly associated with apower level, and a desired throttle setting is one that is at leastroughly associated with an appropriate power level. The desired throttlesetting can be based upon an estimated amount of wireless activity, theratio of non-AP stations to APs, or other parameters. The key withrespect to setting the throttle is to ensure, as much as is possible,that the power provided to a TAP (or the HP components of a TAP) willresult in adequate wireless domain performance, as defined by the humanand/or software agents that manage the wireless domain. Whether the APscan handle the wireless traffic adequately may be based on measurements,empirical or historical data, QoS considerations, or even opinion.

In a static throttle settings implementation, a desired throttle settingwill be the same for a particular amount of wireless activity estimatedfrom wireless activity data obtained through the APs of the wirelessdomain. In this simple implementation, determining the desired throttlesetting involves deriving the setting by comparing the current estimatedwireless activity to a range of values, which may be calculated using aformula, chosen from a data structure stored in memory, or acquired insome other manner. If there are multiple power levels for a TAP, thenthe TAP can be associated with a respective multiple static throttlesettings. If there are multiple TAPs, then each of the TAPs can bethrottled at the same or different levels of estimated wirelessactivity, and each TAP may or may not have different throttle settinggranularity and/or range.

In a dynamic throttle settings implementation, the throttle settings aredynamic in that they vary in response to the wireless activity dataobtained through the APs of the wireless domain. For example, if awireless domain in an office is intended to have higher performance inthe daytime, and more power savings at night, it may be desirable toassociate higher throttle settings for daytime estimated wirelessactivity and associate lower throttle settings for nighttime estimatedwireless activity. Dynamic throttle settings can be set using historicalwireless activity data, including both recent history, and long-termhistory. An example of long-term history might include increases inwireless activity at certain days during the week (e.g., Monday toFriday) at certain times (e.g., 8 A.M., perhaps when many people enterthe wireless domain at the start of work). Dynamic throttle settings canalso be implicitly set in some cases. For example, if a station informs,either implicitly or explicitly, of a need to use relatively highamounts of bandwidth (e.g., for a large file download), throttlesettings could be dynamically dropped relative to estimated wirelessactivity near the station in anticipation of the increased activity. Insome implementations, TAP throttling can be accomplished relativelyrapidly, which reduces the need for dynamic throttle settings. In othercases, TAPs might be relatively slow in throttling up, making dynamicthrottle settings perhaps more valuable to enable anticipation ofwireless resource needs.

In any case, the power level appropriate for the estimated wirelessactivity is determined at a TAP. As various examples were provided abovewith reference to FIG. 2, it is assumed, in order to avoid redundancy,that the TAP operates on a greedy principal in that it determines anappropriate power level based solely upon the estimated wirelessactivity near the TAP.

In the example of FIG. 7, the flowchart 700 continues to decision point706 where it is determined whether a throttle is set to an appropriatelevel. Since the estimated wireless activity is known and the powerlevel appropriate for the wireless activity is known, a comparison of acurrent throttle setting with the desired throttle setting to achievethe desired power level will determine whether the throttle settingshould be adjusted. If it is determined that the throttle is set to anappropriate level (706-Y), then the flowchart 700 returns to module 702and continues as described previously. If, on the other hand, it isdetermined that the throttle is not set to an appropriate level (706-N),then the flowchart continues to module 708 where the TAP is throttled upor down in power to the appropriate throttle setting, and the flowchart700 returns to module 702 and continues as described previously.

FIG. 8 depicts an example of a computing system 800 that isrepresentative of the computing systems discussed herein. The system 800may be a conventional computer system that can be used as a clientcomputer system, such as a wireless client or a workstation, or a servercomputer system. The system 800 includes a device 802, I/O devices 804,and a display device 806. The device 802 includes a processor 808, acommunications interface 810, memory 812, display controller 814,non-volatile storage 816, I/O controller 818, clock 822, and radio 824.The device 802 may be coupled to or include the I/O devices 804 and thedisplay device 806.

The device 802 interfaces to external systems through the communicationsinterface 810, which may include a modem or network interface. It willbe appreciated that the communications interface 810 can be consideredto be part of the system 800 or a part of the device 802. Thecommunications interface 810 can be an analog modem, ISDN modem orterminal adapter, cable modem, token ring IEEE 802.5 interface,Ethernet/IEEE 802.3 interface, wireless 802.11 interface, satellitetransmission interface (e.g. “direct PC”), WiMAX/IEEE 802.16 interface,Bluetooth interface, cellular/mobile phone interface, third generation(3G) mobile phone interface, code division multiple access (CDMA)interface, Evolution-Data Optimized (EVDO) interface, general packetradio service (GPRS) interface, Enhanced GPRS (EDGE/EGPRS), High-SpeedDownlink Packet Access (HSPDA) interface, or other interfaces forcoupling a computer system to other computer systems.

The processor 808 may be, for example, a conventional microprocessorsuch as an Intel Pentium microprocessor or Motorola power PCmicroprocessor. The memory 812 is coupled to the processor 808 by a bus820. The memory 812 can be Dynamic Random Access Memory (DRAM) and canalso include Static RAM (SRAM). The bus 820 couples the processor 808 tothe memory 812, also to the non-volatile storage 816, to the displaycontroller 814, and to the I/O controller 818.

The I/O devices 804 can include a keyboard, disk drives, printers, ascanner, and other input and output devices, including a mouse or otherpointing device. The display controller 814 may control in theconventional manner a display on the display device 806, which can be,for example, a cathode ray tube (CRT) or liquid crystal display (LCD).The display controller 814 and the I/O controller 818 can be implementedwith conventional well known technology.

The non-volatile storage 816 is often a magnetic hard disk, flashmemory, an optical disk, or another form of storage for large amounts ofdata. Some of this data is often written, by a direct memory accessprocess, into memory 812 during execution of software in the device 802.One of skill in the art will immediately recognize that the terms“machine-readable medium” or “computer-readable medium” includes anytype of storage device that is accessible by the processor 808.

Clock 822 can be any kind of oscillating circuit creating an electricalsignal with a precise frequency. In a non-limiting example, clock 822could be a crystal oscillator using the mechanical resonance ofvibrating crystal to generate the electrical signal.

The radio 824 can include any combination of electronic components, forexample, transistors, resistors and capacitors. The radio is operable totransmit and/or receive signals.

The system 800 is one example of many possible computer systems whichhave different architectures. For example, personal computers based onan Intel microprocessor often have multiple buses, one of which can bean I/O bus for the peripherals and one that directly connects theprocessor 808 and the memory 812 (often referred to as a memory bus).The buses are connected together through bridge components that performany necessary translation due to differing bus protocols.

Network computers are another type of computer system that can be usedin conjunction with the teachings provided herein. Network computers donot usually include a hard disk or other mass storage, and theexecutable programs are loaded from a network connection into the memory812 for execution by the processor 808. A Web TV system, which is knownin the art, is also considered to be a computer system, but it may lacksome of the features shown in FIG. 8, such as certain input or outputdevices. A typical computer system will usually include at least aprocessor, memory, and a bus coupling the memory to the processor.

In addition, the system 800 is controlled by operating system softwarewhich includes a file management system, such as a disk operatingsystem, which is part of the operating system software. One example ofoperating system software with its associated file management systemsoftware is the family of operating systems known as Windows® fromMicrosoft Corporation of Redmond, Wash., and their associated filemanagement systems. Another example of operating system software withits associated file management system software is the Linux operatingsystem and its associated file management system. The file managementsystem is typically stored in the non-volatile storage 816 and causesthe processor 808 to execute the various acts required by the operatingsystem to input and output data and to store data in memory, includingstoring files on the non-volatile storage 816.

Some portions of the detailed description are presented in terms ofalgorithms and symbolic representations of operations on data bitswithin a computer memory. These algorithmic descriptions andrepresentations are the means used by those skilled in the dataprocessing arts to most effectively convey the substance of their workto others skilled in the art. An algorithm is here, and generally,conceived to be a self-consistent sequence of operations leading to adesired result. The operations are those requiring physicalmanipulations of physical quantities. Usually, though not necessarily,these quantities take the form of electrical or magnetic signals capableof being stored, transferred, combined, compared, and otherwisemanipulated. It has proven convenient at times, principally for reasonsof common usage, to refer to these signals as bits, values, elements,symbols, characters, terms, numbers, or the like.

It should be borne in mind, however, that all of these and similar termsare to be associated with the appropriate physical quantities and aremerely convenient labels applied to these quantities. Unlessspecifically stated otherwise as apparent from the following discussion,it is appreciated that throughout the description, discussions utilizingterms such as “processing” or “computing” or “calculating” or“determining” or “displaying” or the like, refer to the action andprocesses of a computer system, or similar electronic computing device,that manipulates and transforms data represented as physical(electronic) quantities within the computer system's registers andmemories into other data similarly represented as physical quantitieswithin the computer system memories or registers or other suchinformation storage, transmission or display devices.

The present example also relates to apparatus for performing theoperations herein. This Apparatus may be specially constructed for therequired purposes, or it may comprise a general purpose computerselectively activated or reconfigured by a computer program stored inthe computer. Such a computer program may be stored in a computerreadable storage medium, such as, but is not limited to, read-onlymemories (ROMs), random access memories (RAMs), EPROMs, EEPROMs, flashmemory, magnetic or optical cards, any type of disk including floppydisks, optical disks, CD-ROMs, and magnetic-optical disks, or any typeof media suitable for storing electronic instructions, and each coupledto a computer system bus.

The algorithms and displays presented herein are not inherently relatedto any particular computer or other Apparatus. Various general purposesystems may be used with programs in accordance with the teachingsherein, or it may prove convenient to construct more specializedApparatus to perform the required method steps. The required structurefor a variety of these systems will appear from the description below.In addition, the present example is not described with reference to anyparticular programming language, and various examples may thus beimplemented using a variety of programming languages.

It will be appreciated to those skilled in the art that the precedingexamples are exemplary and not limiting. It is intended that allpermutations, enhancements, equivalents, and improvements thereto thatare apparent to those skilled in the art upon a reading of thespecification and a study of the drawings are included within the truespirit and scope of the present disclosure. It is therefore intendedthat the following appended claims include all such modifications,permutations and equivalents as fall within the true spirit and scope ofthese teachings.

1. A method comprising: monitoring wireless activity in a wirelessdomain; determining a power level appropriate for the wireless activity;adjusting a throttle setting of a throttleable access point (TAP) from afirst throttle setting associated with a low power (LP) mode to a secondthrottle setting associated with a high power (HP) mode, wherein thesecond throttle setting corresponds to the power level determined to beappropriate for the wireless activity, and wherein adjusting thethrottle setting to the second throttle setting causes the TAP to enterthe HP mode.
 2. The method of claim 1, further comprising: monitoringthe wireless domain to obtain the wireless activity data; estimatingwireless activity using the wireless activity data.
 3. The method ofclaim 2, further comprising receiving at least a portion of the wirelessactivity data from the TAP.
 4. The method of claim 2, wherein the TAP isa first AP in the wireless domain, further comprising receiving at leasta portion of the wireless activity data from a second AP in the wirelessdomain.
 5. The method of claim 1, wherein a first antenna is active atthe TAP, further comprising activating a second antenna at the TAP inresponse to entering the HP mode.
 6. The method of claim 1, furthercomprising supplying power over Ethernet (PoE) to the TAP.
 7. The methodof claim 1, further comprising using a single spatial stream when theTAP is in the LP mode and using multiple spatial streams when the TAP isin the HP mode.
 8. The method of claim 1, further comprising spatiallymultiplexing multiple independent data streams, transferred at leastapproximately simultaneously within one spectral channel of bandwidth,when the TAP is in the HP mode.
 9. The method of claim 1, furthercomprising at least approximately simultaneously transmitting overmultiple non-overlapping channels when the TAP is in the HP mode. 10.The method of claim 1, further comprising operating the TAP incompliance with at least a portion of the IEEE 802.11n standard.
 11. Asystem comprising: an access point (AP) interface; a wireless activitythreshold module; a wireless activity analysis module, coupled to the APinterface and to the wireless activity threshold module, wherein inoperation the wireless activity analysis module receives wirelessactivity data associated with a wireless domain from the AP interface,receives a wireless activity threshold from the wireless activitythreshold module, compares estimated wireless activity associated withthe wireless activity data to the wireless activity threshold, andprovides throttleable AP (TAP) throttling data to the AP interface foroutput to a TAP when the estimated wireless activity exceeds thewireless activity threshold.
 12. The system of claim 11, furthercomprising the TAP coupled to the AP interface, wherein in operation theTAP provides at least a portion of the wireless activity data.
 13. Thesystem of claim 11, wherein the TAP is a first AP, further comprising asecond AP coupled to the AP interface, wherein in operation the secondAP provides at least a portion of the wireless activity data.
 14. Thesystem of claim 11, further comprising the TAP coupled to the APinterface, wherein in operation the TAP receives the TAP throttling dataor a command derived from the TAP throttling data, and switches from alow power mode to a higher power mode in response to the TAP throttlingdata or the command derived from the TAP throttling data.
 15. The systemof claim 11, wherein the wireless activity data is associated with IEEE802.11n communications.
 16. A system comprising: a power interface; lowpower (LP) access point (AP) components, including a first antenna,coupled to the power interface, wherein, in operation, the LP APcomponents receive power from the power interface and providefunctionality sufficient for a device to operate as an AP in a wirelessdomain using the first antenna; a throttle coupled to the powerinterface, wherein a first throttle setting of the throttle isassociated with a LP mode and a second throttle setting of the throttleis associated with a high power (HP) mode; a second antenna, coupled tothe power interface, wherein, in the LP mode, in operation, the secondantenna is not used to transmit in the wireless domain, and wherein, inthe HP mode, in operation, the second antenna is used to transmit in thewireless domain simultaneously with the first antenna in one spectralchannel of bandwidth.
 17. The system of claim 16, further comprising acontroller interface coupled to the throttle, wherein, in operation, aTAP throttling signal received on the controller interface causes thethrottle to increase or decrease the amount of power supplied from thepower interface to the second antenna.
 18. The system of claim 16,further comprising a controller interface coupled to the throttle,wherein, in operation, TAP throttling data received on the controllerinterface causes the throttle to calculate an appropriate throttlesetting, and increase or decrease the amount of power supplied from thepower interface to the second antenna in accordance with thecalculation.
 19. The system of claim 16, further comprising HP APcomponents coupled to the power interface, wherein the second antenna isincluded in the HP AP components.
 20. The system of claim 16, wherein,in the HP mode, the first antenna and second antenna operate incompliance with at least a portion of the IEEE 802.11n standard.